-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[CF1] tunnel run flag note #20781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CF1] tunnel run flag note #20781
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryUpdated documentation for tunnel run parameters and clarified the creation of remotely-managed tunnels.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add What is Hyperlint?Hyperlint is an AI agent that helps you write, edit, and maintain your documentation. Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation. |
|
|
||
| :::note | ||
|
|
||
| For locally-managed tunnels and Windows [remotely-managed tunnels](/cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/#remotely-managed-tunnel) only. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd frame this in terms of package manager vs no package manager. Technically no-autoupdate would also work for non-Windows tunnels if you didn't use a package manager.
Does not apply if you installed cloudflared using a package manager (for example, by following the macOS or Debian installation instructions in the dashboard). You can check if cloudflared was installed by a package manager by running ls -la /usr/local/etc/cloudflared/ and looking for .installedFromPackageManager appears in the output. If so, disable auto-update in the package manager.
Consider making a partial out of the matching sentence in https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/downloads/update-cloudflared/#remotely-managed-tunnels
* [CF1] tunnel run flag note * update step 2 * link * error * partial
Summary
13940
Documentation checklist